-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(RHOAIENG-15495): Add component metadata manifest #374
feat(RHOAIENG-15495): Add component metadata manifest #374
Conversation
Refer to [RHOAIENG-15495](https://issues.redhat.com/browse/RHOAIENG-15495)
PR image build and manifest generation completed successfully! 📦 PR image: 📦 LMES driver image: 📦 LMES job image: 🗂️ CI manifests
|
@ruivieira: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Do you plan to make this automatic? |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: danielezonca, RobGeada The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@danielezonca I could include some automation in a future PR. Perhaps getting the values from the release branch name? I think it's better than tag-based, since in that case the changes would happen after the tag is pushed. |
* feat(RHOAIENG-15495): Add component metadata manifest Refer to [RHOAIENG-15495](https://issues.redhat.com/browse/RHOAIENG-15495) * Add new line to fix linting (cherry picked from commit c9467b5)
Refer to RHOAIENG-15495
Add template
component_metadata
to be populated with release values when performing community releases.